chore: standardize CODEOWNERS for giants-kinde and sdk-engineers - #27

🏁 Script executed:

#!/bin/bash
set -eu
printf '%s\n' '--- .vscode/launch.json ---'
cat -n .vscode/launch.json
printf '%s\n' '--- AWS_PROFILE references ---'
rg -n -C 2 'AWS_PROFILE|flo-ct-flo360|aws profile|AWS account' --glob '!node_modules' --glob '!dist' --glob '!build' .

Repository: kinde-starter-kits/python-starter-kit

Length of output: 2236

• .vscode/launch.json#L14-L16 (this comment)
• .vscode/launch.json#L26-L28
• .vscode/launch.json#L38-L40

🏁 Script executed:

set -eu
printf '%s\n' '--- .vscode/tasks.json ---'
cat -n .vscode/tasks.json
printf '%s\n' '--- .vscode/settings.json ---'
cat -n .vscode/settings.json
printf '%s\n' '--- package manifests ---'
for f in package.json; do
  if [ -f "$f" ]; then
    cat -n "$f" | sed -n '1,180p'
  fi
done

Repository: kinde-starter-kits/python-starter-kit

Length of output: 2235

🌐 Web query:

official Visual Studio Code documentation tasks.json runOptions runOn folderOpen workspace settings schema

💡 Result:

<search_synthesis>
In Visual Studio Code, you can configure a task to run automatically when a workspace or folder is opened by using the runOptions property in your tasks.json file [1][2][3]. Configuration To enable this behavior, add the runOptions property to your specific task definition within tasks.json and set the runOn property to "folderOpen" [1][4][5]. { "version": "2.0.0", "tasks": [ { "label": "My Auto Task", "type": "shell", "command": "echo &#39;Hello World&#39;", "runOptions": { "runOn": "folderOpen" } } ] } Security and Enabling Automatic Tasks For security reasons, VS Code does not automatically run these tasks unless you explicitly permit them [1][2]. Automatic tasks will never run in an untrusted workspace [1][2]. You can control whether automatic tasks are permitted using the task.allowAutomaticTasks setting [1][2]. This can be configured in your User or Workspace settings: { "task.allowAutomaticTasks": "on" } The available values for this setting are: - off (default): Disables automatic task execution. You will be prompted to allow or disallow them when opening a workspace [1][2]. - on: Automatically runs tasks configured with "runOn": "folderOpen" in trusted workspaces without prompting [1][2]. You can also manage these permissions manually through the Command Palette (Ctrl+Shift+P or Cmd+Shift+P) by searching for "Manage Automatic Tasks" [1][2][3]. JSON Schema Details According to the official VS Code task schema, the runOptions object includes the following properties [4][6]: - runOn: A string that determines when the task runs. Valid values include "default" (run only via the Run Task command) and "folderOpen" [4][6]. - reevaluateOnRerun: A boolean that controls whether variables are reevaluated when executing the "Rerun Last Task" command (default is true) [1][4][6]. Additional configuration properties like instanceLimit (the number of simultaneous instances, default 1) and instancePolicy (the strategy when the limit is reached, such as "terminateNewest" or "prompt") are also available under runOptions [6][7].
</search_synthesis>

<source_evidence>

Citations:

• 1: https://code.visualstudio.com/docs/debugtest/tasks
• 2: https://github.com/microsoft/vscode-docs/blob/main/docs/debugtest/tasks.md
• 3: https://frontendmasters.com/blog/vs-code-auto-run-commands/
• 4: https://code.visualstudio.com/docs/reference/tasks-appendix
• 5: https://stackoverflow.com/questions/34103549/can-i-automatically-start-a-task-when-a-folder-is-opened
• 6: https://github.com/microsoft/vscode/blob/master/src/vs/workbench/contrib/tasks/common/jsonSchema_v2.ts
• 7: https://github.com/microsoft/vscode/blob/ae7dce46/src/vs/workbench/contrib/tasks/common/jsonSchema_v2.ts

• .vscode/tasks.json#L14-L30 (this comment)
• .vscode/settings.json#L17-L22